IoT TAG and invivo sensor system and communication method

ABSTRACT

A sensor system is provided. The sensor system includes: a battery that powers the sensor system; a radio-frequency identification (RFID) tag that stores a unique identifier of the sensor system; a sensor that provides a sensing data for the sensor system; an internet of things (IoT) transceiver that communicates with an access point in an IoT system; and a processor that receives the sensing data from the sensor and controls an activation of the sensor and a frequency of communication of the IoT transceiver with the access point.

BACKGROUND

Availability of the status of various physical assets can be beneficial or even essential. For example, it may be useful to track the location of moving items or persons, for various reasons such as to provide security, to optimize certain operations, e.g., in industrial environments or logistic applications, and/or to provide useful instructions to a tracked person. Further, monitoring stationary objects may also be useful. Such a stationary object may be, for example, a sensor that can be queried to obtain information about the environment surrounding the sensor.

SUMMARY

In general, in one aspect, the invention relates to a sensor system comprising: a battery that powers the sensor system; a radio-frequency identification (RFID) tag that stores a unique identifier of the sensor system; a sensor that provides a sensing data for the sensor system; an internet of things (IoT) transceiver that communicates with an access point in an IoT system; and a processor that: receives the sensing data from the sensor; and controls an activation of the sensor and a frequency of communication of the IoT transceiver with the access point.

In general, in one aspect, the invention relates to a sensor system comprising: a battery that powers the sensor system; a sensor that provides a sensing data for the sensor system; a transceiver that communicates with an IoT sensor system in an IoT system; a processor that: receives the sensing data from the sensor; and controls an activation of the sensor and a frequency of communication of the transceiver with the IoT sensor.

In general, in one aspect, the invention relates to a communication method between an Internet of Things (IoT) sensor, one or more in-vivo sensors associated with the IoT sensor, and an access point in an IoT system, the communication method comprising: synchronizing the IoT sensor with the access point; re-synchronizing the IoT sensor with the access point during a predetermined period when synchronization is lost; measuring, by the IoT sensor and the one or more in-vivo sensors, a sensing data; transmitting, by the one or more in-vivo sensors to the IoT sensor, the sensing data measured by one or more in-vivo sensors; merging, by the IOT sensor, the sensing data measured by the one or more in-vivo sensors with the sensing data measured by the IoT sensor; and transmitting, by the IoT sensor, the merged sensing data to the access point.

BRIEF DESCRIPTION OF DRAWINGS

FIGS. 1A-1H show systems for monitoring assets, in accordance with one or more embodiments of the invention.

FIGS. 2A and 2B show a hub-cloud configuration of a system for monitoring assets, in accordance with one or more embodiments of the invention.

FIGS. 3A-3G show access points of a system for monitoring assets, in accordance with one or more embodiments of the invention.

FIGS. 4A-4C show diagrams of monitoring devices for a system for monitoring assets, in accordance with one or more embodiments of the invention.

FIGS. 5A-5C show diagrams of peripheral sensor systems for a system for monitoring assets, in accordance with one or more embodiments.

FIG. 6 shows an Internet of Things (IoT) communication protocol overlay, in accordance with one or more embodiments of the invention.

FIG. 7 shows a flowchart describing methods for monitoring assets, in accordance with one or more embodiments of the invention.

FIG. 8 shows a flowchart of sensor transmission protocol for the monitoring device of FIGS. 4A-4C, in accordance with one or more embodiments.

FIG. 9 shows a sensor protocol diagram, in accordance with one or more embodiments.

FIG. 10 shows a flowchart of the sensing data transmission using the IoT sensor protocol diagram of FIG. 9, in accordance to one or more embodiments.

FIG. 11 shows a flowchart of an in-vivo sensor activation protocol, in accordance to one or more embodiments.

FIG. 12 shows a computing system in accordance with one or more embodiments of the invention.

DETAILED DESCRIPTION

Specific embodiments of the invention will now be described in detail with reference to the accompanying figures. Like elements in the various figures are denoted by like reference numerals for consistency. Like elements may not be labeled in all figures for the sake of simplicity.

In the following detailed description of embodiments of the invention, numerous specific details are set forth in order to provide a more thorough understanding of the invention. However, it will be apparent to one of ordinary skill in the art that the invention may be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description.

Throughout the application, ordinal numbers (e.g., first, second, third, etc.) may be used as an adjective for an element (i.e., any noun in the application). The use of ordinal numbers does not imply or create a particular ordering of the elements or limit any element to being only a single element unless expressly disclosed, such as by the use of the terms “before,” “after,” “single,” and other such terminology. Rather, the use of ordinal numbers is to distinguish between the elements. By way of an example, a first element is distinct from a second element, and the first element may encompass more than one element and succeed (or precede) the second element in an ordering of elements.

In the following description of FIGS. 1A-12, any component described with regard to a figure, in various embodiments of the invention, may be equivalent to one or more like-named components described with regard to any other figure. For brevity, descriptions of these components will not be repeated with regard to each figure. Thus, each and every embodiment of the components of each figure is incorporated by reference and assumed to be optionally present within every other figure having one or more like-named components. Additionally, in accordance with various embodiments of the invention, any description of the components of a figure is to be interpreted as an optional embodiment which may be implemented in addition to, in conjunction with, or in place of the embodiments described with regard to a corresponding like-named component in any other figure.

It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a horizontal beam” includes reference to one or more of such beams.

Terms such as “approximately,” “substantially,” etc., mean that the recited characteristic, parameter, or value need not be achieved exactly, but that deviations or variations, including for example, tolerances, measurement error, measurement accuracy limitations and other factors known to those of skill in the art, may occur in amounts that do not preclude the effect the characteristic was intended to provide.

It is to be understood that, one or more of the steps shown in the flowcharts may be omitted, repeated, and/or performed in a different order than the order shown. Accordingly, the scope of the invention should not be considered limited to the specific arrangement of steps shown in the flowcharts.

Although multiple dependent claims are not introduced, it would be apparent to one of ordinary skill that the subject matter of the dependent claims of one or more embodiments may be combined with other dependent claims.

In general, embodiments of the invention are directed to a sensor system and a sensor system communication method used in a system and a method for monitoring assets. An asset may be anything of interest and/or value for which it is valuable to gather information about the status of the asset. Consider, the following examples:

-   -   A hospital that is specialized in the treatment of patients with         dementia. If these patients are allowed to move freely within         the hospital environment, it may be important to be able to         determine their location at any time. Further these patients may         suffer from additional conditions that may require continuous         monitoring of other variables such as heart rate, blood         pressure, etc.     -   In a luggage transportation system of a major airport, the         ability to locate any luggage item at any time, while being         processed by the luggage transportation system, would be highly         beneficial.     -   In the oil and gas industry, it may be beneficial to monitor         pipelines or other equipment to ensure safety and productivity.     -   In a warehouse, it may be useful to track employees, goods         and/or equipment to optimize operations.     -   In a ranching environment, it may be beneficial to track the         location and physiological status of cattle, sheep, goats, and         other herds of farm animals.

Those skilled in the art will appreciate that the invention is not limited to the above examples. Embodiments of the invention may be used in any environment, including commercial, industrial, residential and natural environments of any size to monitor moving or stationary assets including, but not limited to, humans, animals, devices, products, or any other type of item. Further, the monitoring includes obtaining any type of information such as a location or a measurement of any variable.

FIGS. 1A-1H show systems for monitoring assets, in accordance with one or more embodiments of the invention. Turning to FIG. 1A, a monitored environment (100), in accordance with one or more embodiments of the invention, is shown. The monitored environment (100) may be any type of environment that is monitored using the monitoring system (110). A monitored environment may be, for example, an outdoor environment, e.g., in the oil and gas industry, or an area where environmental monitoring is performed, e.g., in a national park. A monitored environment may also be an indoor environment, for example, a warehouse, a school, a hospital, a prison, etc. A monitored environment may also include a combination of indoor and outdoor environments, e.g., when a campus of a public or private institution is monitored. Any environment that is equipped with a monitoring system (110) may be considered a monitored environment (100).

Within the monitored environment (100), monitored assets (102), may be tracked or monitored by the monitoring system (110). Monitored assets (102) may include stationary and/or moving assets. A moving asset may be a person, an animal, equipment (e.g., a forklift truck), goods, products or other items, including luggage, shipments such as boxes or containers, etc. A stationary asset may be anything equipped with sensors to monitor function and/or environmental conditions. Examples for such stationary assets include weather stations, pumps, pipelines, refrigeration equipment, air quality sensors, etc. The monitoring may be performed by a monitoring device (104) that is carried by the monitored asset or that is attached or installed on the monitored asset.

In one or more embodiments of the invention, a monitored asset (102) may further be controlled via the monitoring system (110). A monitoring device (104) may interface with the monitored asset (102) to, for example, activate or deactivate functions, switch modes, etc. If the monitoring device (104) is also used for sensing, a closed loop operation via the monitoring system (110) may be implemented. Based on sensed conditions, the monitored asset may be controlled in order to change the sensed conditions.

An access point (112), in one or more embodiments of the invention, is configured to communicate with the monitoring devices (104) of the monitored assets (102) via an Internet of Things (IoT) link (106). The access point may further interface with a hub (118), which may perform processing of the data received from the monitored assets via the access points, as further described below. In one or more embodiments of the invention, data gathered from the monitored assets is uploaded to a cloud environment (150), from where they may be accessible to users. Additionally or alternatively, the data may also be locally accessible via the hub or via the access point, as further described below. Each of the components of the system for monitoring assets is subsequently described in detail, with reference to FIGS. 2A-7.

Turning to FIG. 1B, an alternative configuration of a system for monitoring assets (110), in accordance with one or more embodiments of the invention, is shown. Unlike the system shown in FIG. 1A, the system of FIG. 1B includes multiple access points (112A, 112B). Each access point may have a limited range that may depend on the transmission power of the access point, but also on the transmission power of the monitoring devices (104) of the monitored assets (102). Accordingly, in order to cover larger environments (100) with monitoring services, multiple access points may be placed at different locations in the environment. FIG. 1B shows a primary access point (112A) and two secondary access points (112B). While the primary access point (112A) may directly interface with the hub (118), e.g., using a wired broadband link such as an Ethernet interface, the secondary access points may interface with the primary access point (112A) using a broadband link (120) such as a wireless local area network (WLAN) based on, e.g., the Wi-Fi standard. Using additional access points, distributed across the monitored environment (100), larger areas may thus be covered by the system for monitoring assets (110). Those skilled in the art will appreciate that various configurations of multiple access points are feasible without departing from the invention. For example, systems for monitoring assets may include any number of access points to monitor environments of any size. Further, multiple access points may directly interface with the hub (similar to the primary access point (112A)). Alternatively or additionally, multiple access points may increase the monitored area using a daisy chain configuration (i.e., tertiary access points may interface with the secondary access points, analogous to how the secondary access points interface with the primary access point). Further, in hybrid configurations, some access points may be daisy-chained, whereas other access points may directly interface with the hub. In one embodiment of the invention, an access point or multiple access points may be directly connected to the cloud, e.g., when a reliable connection to the cloud is continuously available.

Turning to FIG. 1C, another alternative configuration of a system for monitoring assets, in accordance with one or more embodiments of the invention, is shown. The system includes additional components that may facilitate the use of the monitoring system and/or provide additional features. In one embodiment of the invention, the broadband link (120) of the access point (112) is used to provide user access to the monitoring system (110). More specifically, user devices such as smartphones (128) or laptops (130) may connect to the access point (112) via the broadband link (120) in order to obtain monitoring data, to configure the monitoring system, etc. Data that is provided by the monitoring devices (104) and/or monitoring device data that has been previously collected, processed and/or stored by the hub (118) may be obtained via a hub/cloud platform, described in FIGS. 2A and 2B.

In one or more embodiments of the invention, the broadband link may further be used to interface additional devices with access points (112) of the monitoring system (110). In FIG. 1C, a drone (118) is shown, communicating with the access point (112) via the broadband link (120). The drone may further enhance the monitoring capabilities of the monitoring system (110). The drone may, for example, be equipped with a camera and/or other sensors and may be in contact with various access points, depending on the drone's current location in the monitored environment (100). The drone may further not necessarily be in continuous contact with an access point and may, instead, operate autonomously and may only require periodic contact with an access point. One or more drones (118) may be used to visually inspect environments. Multispectral cameras and/or mosaic photography may be used to monitor environmental conditions and/or activity in the monitored environment using additional analytics software.

Other sensors that rely on a broadband link (160) via one of the access points (112) may be part of the monitoring system as well. For example, cameras that are equipped with a Wi-Fi interface may be used to visually monitor certain areas of the monitored environment (100). Such cameras may include motion detection to detect activities including expected or desired activity, but also unexpected activity, such as intrusions. Additionally or alternatively, cameras may provide still photos, video clips or live videos and/or alarms based on a detection of certain events in the videos or photos. In addition, the broadband link (160) may be used for any other purposes such as voice over IP and/or for any other high data rate service.

In one or more embodiments of the invention, the monitoring system (110), using the IoT link (106), interfaces not only with the monitoring devices (104), but also with other sensors (122). The other sensors may perform environmental measurements such as air temperature, humidity, or may be used to monitor equipment such as pumps, storage tanks, pipelines, etc.

One or more embodiments of the invention further support additional sensing equipment in the form of peripheral sensors (124). A peripheral sensor may be used to acquire additional measurements that may not be obtainable by the monitoring device (104) itself. The peripheral sensors thus further extend the monitoring functionalities provided by the monitoring device (104). Any number of peripheral sensors (124) may be used in conjunction with a monitoring device (104). A local sensor link (126) may transmit the measurements obtained by the peripheral sensor (124) to the monitoring device (104), which may relay these measurements to one of the access points (112). An exemplary peripheral sensor is further discussed below, with reference to FIGS. 5A-5C.

In one or more embodiments of the invention, the access point (112) is a two-tier access point equipped with a first tier broadband communication interface and a second tier narrowband communication interface. The first tier broadband communication interface provides the broadband link (120) and the second tier narrowband interface provides the IoT link (106). While the narrowband link may provide coverage of a comparatively large area at a reduced data rate that may be particularly suitable for monitoring devices (104) and other sensors (122), the broadband link may provide coverage of a comparatively smaller area at a higher data rate that may be suitable to serve other devices such as laptops (130), smartphones (128), or other broadband equipment, including drones (118), cameras (not shown), etc. The broadband link may further be used to establish a mesh with other access points, as previously shown in FIG. 1B. In one embodiment of the invention, the monitoring system includes a three-tier network that, in addition to the two tiers of the access point, includes a third tier formed by the local sensor link (126), as previously described.

FIG. 1C further shows a radio frequency identification (RFID) wand. The RFID wand may be used, in proximity of an RFID transmitter to read out basic information provided by the RFID transmitter. The RFID transmitter may be a component of the monitoring device (104) or of a peripheral sensor (124) and may provide static information such an ID. Consider, for example, the use of monitoring devices (104) to track luggage at an airport. Airport security may then be able to obtain the identity of luggage equipped with a monitoring device, using the RFID wand. The RFID wand (or stationary RFID readers) may further be used in other security and/or monitoring applications such as check-through scenarios at facility entries and exists, clock-in/clock-out applications, etc. The RFID wand may be equipped with a GPS unit, enabling obtaining a location at the time when RFID information is obtained from an RFID transmitter. Additionally or alternatively, the RFID wand may be equipped with an IoT interface enabling the RFID wand (132) to communicate with one or more access points (112) in order to obtain a location and/or to upload RFID information obtained from an RFID transmitter. Further, RFID wands, in accordance with one or more embodiments of the invention, may be equipped with a narrowband communication interface to establish a narrowband link (136), e.g., a Bluetooth link to another device such as a smartphone (128) or a laptop (130). The narrowband link may enable a user to access RFID data either spontaneously, e.g. as an RFID transmitter is read, or in bulk readouts, after a number of RFID transmitters have been scanned.

Turning to FIG. 1D, various options for interfacing the hub (118) with the computing devices in the cloud (150), e.g., using the Internet, are illustrated, in accordance with one or more embodiments of the invention. A wired backhaul uplink (140), a cellular backhaul uplink (142) and/or a satellite backhaul uplink may be used to interface the hub (118) with a cloud computing device, e.g., the cloud server (152). Alternatively, any other data connection, including any kind of point-to-point or multipoint connection that is at least temporarily available may be used as a backhaul link. In one embodiment of the invention, no backhaul link is used, i.e., the hub (118) is operating without an interface to the cloud (150), and therefore may only be accessed using local computing devices accessing the hub (118) via the access point (112), as previously described with reference to FIG. 1C. Alternatively, in one embodiment of the invention, no hub is used, i.e., the access point(s) may be directly connected to the backhaul link. Such a configuration may be suitable if the backhaul link is considered very reliable. Alternatively, if the backhaul link is considered less reliable, the hub may provide full or at least partial functionality while the cloud is not reachable.

The wired backhaul link (140) may be, for example, a wired Ethernet connection to an Internet service provider, a fiber-optic connection, a DSL Internet connection, a cable Internet connection, etc. Any type of wired data interface suitable to connect the hub to the cloud environment (150) may be used. The cellular backhaul link may be any type of cellular data connection such as a 3G, LTE or 5G data connection. Those skilled in the art will appreciate that any type of wired or wireless data link may be used as a backhaul link, without departing from the invention.

Turning to FIG. 1E, an exemplary radio signal coverage by a single access point (112), in accordance with one or more embodiments of the invention, is shown. As illustrated, a smaller region surrounding the access point receives broadband coverage (dashed circle), e.g., via the Wi-Fi signal of the access point. Within this zone, sensors that require a broadband link, e.g. cameras, may be installed. A larger region, surrounding the access point, receives narrowband coverage by the IoT link (108) (solid circle). While less data may be transmitted using the IoT link, data transmission using the IoT link may require less power and may be feasible over longer distances, in comparison to the broadband link. A monitoring device (104), which is typically battery-powered, therefore may use the IoT link rather than the broadband link. Those skilled in the art may appreciate that the areas that receive broadband and narrowband coverage depend on various factors, including the transmission power of the components involved in data transmissions, the types of antennas being used, terrain features, etc.

Turning to FIG. 1F, an exemplary radio signal coverage by multiple access points (112), in accordance with one or more embodiments of the invention, is shown. In the shown configuration, the access points are spaced such that there is significant overlap between the broadband coverage (dashed circles) provided by the different access points, but also between the narrowband coverage (solid circles) provided by the different access points. Using the set of access points, a coverage region (196) is entirely covered by narrowband signals of at least three access points. In one or more embodiments of the invention, overlap of narrowband coverage provided by multiple access points is desirable. Specifically, in a region where a sensor receives narrowband coverage by at least three narrowband signals (e.g., IoT signals), the signals of a monitoring device, received by at least three access points may be used to determine the location of the monitoring device, thus enabling, for example, location tracking of a monitored asset (102) equipped with a monitoring device (104). The location of a monitoring device may be determined using time difference of arrival (TDOA) methods. Accordingly, location tracking using TDOA methods may be performed in the coverage region (196) in which at least three access points may receive transmissions sent by the monitoring device. TDOA positioning may provide moderately accurate location information (e.g. with an accuracy of approximately 30-75 m), although the accuracy may deteriorate when the quality of the reception at one or more of the access points is poor. The measurement accuracy may, however, not be strongly affected by the presence of buildings and foliage. Alternatively, received signal strength indication (RSSI) positioning may provide location information with limited accuracy, (frequently no more accurate than approximately 75 m), and may allow positioning even under difficult conditions, e.g., when fewer than three access points are available. Further, if equipped with a global positioning system (GPS) receiver, the monitoring device's location may be determined using the GPS receiver. GPS positioning does not rely on the exchange of signals with access points and may thus be available anywhere, even outside the coverage region (196), although power requirements may be significantly higher when relying on GPS. Further, GPS signals may be blocked by structures, foliage, etc. However, the accuracy is typically higher than the accuracy of the TDOA and RSSI methods.

Accordingly, to enable energy efficient location determination in certain regions, access points may be strategically placed to have overlapping coverage regions, thereby not requiring the use of power consuming GPS positioning. In regions where TDOA based location services are desired, a dense grid of access points with a high degree of overlap may be installed to ensure that overlapping coverage is provided by at least three access points, whereas a sparse grid of access points may be installed in other regions. In these other regions, less accurate RSSI positioning may be used, or if an accurate location is required, GPS positioning may be used.

Turning to FIG. 1G, an exemplary radio signal coverage by multiple access points (112A, 112B), in accordance with one or more embodiments of the invention, is shown. To cover large areas effectively while allowing for extended battery life, up to years, access points may need to be deployed strategically to cover the desired monitored environment. The configuration shown in FIG. 1G uses a primary access point (112A) that directly interfaces with a hub (118) and provides an interface to the secondary access points (112B). Using the set of access points, a coverage region (198) is entirely covered by a narrowband signal (solid circles), while some areas are also covered by a broadband signal (dashed circles). In the exemplary configuration shown in FIG. 1G, the left part of the coverage region (198) is covered by sparsely placed access points, where broadband coverage regions are non-overlapping. In contrast, the right part of the coverage region (198) is covered by densely placed access points, where broadband coverage is overlapping, thus establishing a contiguous region with broadband signal coverage. Those areas may, thus, serve different purposes. For example, the left part may be used to monitor sensors that merely require a narrowband communication interface, e.g., weather sensors or monitoring devices for assets that do not require TDOA tracking. In contrast, the right part may be used for a drone surveillance that requires a continuous broadband signal. Those skilled in the art will appreciate that even though FIG. 1G shows the primary access point (112A) interfacing with a hub (118), the hub is not necessarily required. For example, the primary access point (112A) may directly interface with the cloud environment (150). Further, to provide coverage for larger areas and/or for larger numbers of assets to be tracked, additional access points, including primary and/or secondary access points and/or additional hubs may be deployed.

Turning to FIG. 1H, an exemplary monitoring system (110) that includes multiple network segments (192, 194), in accordance with one or more embodiments of the invention, is shown. Each of the network segments (192, 194), is equipped with a hub (118) and multiple access points (112), providing monitoring coverage. Alternatively, these network segments may be operated without hubs. Further, both network segments operate using the same RF plan, i.e., using the same transmission protocol and frequencies, further described in FIG. 6. Network segment 1 (192) is configured as a multitenant site, i.e., multiple customers (customers 1-4, site A) are served by the network segment. Consider, for example, a monitoring system (110) that is installed in a healthcare facility that is shared by multiple care providers. Assume that these care providers have in common that their patients require monitoring. Accordingly, the care providers agree to have a common monitoring system installed by a monitoring service provider that offers the monitoring as a service. Customer 1 is an assisted living provider with patients that may suffer from dementia and may therefore get disoriented within their environment. Staff therefore needs to be able to locate these patients. Customer 2 is a nursing home provider with patients that temporarily need support and may spontaneously need assistance, thus requiring localization of patients whenever they need assistance. Customer 3 is a mental health care center. Patients may be violent or may attempt to escape and therefore need to be monitored as well. Customer 4 is a drug rehabilitation center, where patients may also be violent and may try to escape and therefore also need to be monitored. Patients of the assisted living facility and the nursing home facility may be allowed to freely move between the assisted living facility and the nursing home facility. In contrast, allowed movement of patients of the mental health center and the drug rehabilitation center is strictly limited to areas within their respective facilities. The assisted living provider further operates a second assisted living facility on site B that is separate from site A, and that is covered by network segment 2 (194). Because network segments 1 and 2 belong to the same monitoring system, information about devices may be exchanged between the network segments. Accordingly, moving patients between site A and site B is straightforward. The scenario of FIG. 1H thus illustrates a multitenant, multisite monitoring system, in accordance with one or more embodiments of the invention. Those skilled in the art will appreciate that monitoring systems, in accordance with one or more embodiments of the invention, are fully scalable. For example, monitoring systems may include any number of sites, any number of customers and any number of patients or, generally speaking, assets to be monitored. Further, monitoring systems, in accordance with one or more embodiments of the invention, may be globally distributed. For example, sites A and B may be on different continents. Network segments may grow arbitrarily large, with any number of access points and/or monitoring devices. However, eventually a network segment with numerous devices may become congested, or the hub of the network segment may be overwhelmed by the incoming volume of data. In such a scenario, the network segment may be split into two or more separate network segments, each with its own hub and access points.

Turning to FIG. 2A, a hub-cloud configuration of a system for monitoring assets, in accordance with one or more embodiments of the invention, is shown. The hub-cloud configuration includes the hub (210), the cloud (230), and the user application (250). A hub/cloud platform (270), jointly executing on the hub (270) and in the cloud (230) in a distributed manner, provides back end-support for various components of the monitoring system (110), as further described with reference to FIG. 2B. A user application (250) may be relied upon by a user to access the hub/cloud platform (270) via the hub (210) and/or via the cloud (230). Each of these components is subsequently described.

Services, made available through the hub/cloud platform (270) may include, for example, providing data, gathered by the monitoring system (110), to the user, enabling the user to configure the monitoring system, etc. The hub/cloud platform (270) may be accessed by a user using the user application (250), which may be executing on a computing device such as a smartphone or a laptop. The user application (250), thus, may provide a user interface configured to enable the user to access the hub/cloud platform, and to receive notifications on critical events. The user application may include for example, alert displays, status messages, data visualization capabilities, control and configuration capabilities, etc. The user application may further provide data entry fields (e.g., to configure the monitoring system), specialized control interfaces (e.g., to control a drone), voice over IP (VoIP) and/or push to talk interfaces and other communication interfaces that are supported by the broadband links provided by the access points. Alternative implementations of the user application (250) may operate on other devices, e.g., on an audio alert device.

Depending on whether the user application (250) accesses the hub/cloud platform (270) via the hub (210) or via the cloud (230), the user application (250) may interface with the hub/cloud platform via the app service (212) of the hub (210) (e.g., using a smartphone's Wi-Fi interface) or via the app service (232) of the cloud (230) (e.g., using the smartphone's LTE interface). When a user is on-site, e.g., directly connected to an access point using a Wi-Fi link, accessing the hub/cloud platform (270) may be particularly low-latency because the interaction of the user's computing device with the hub is local.

The hub (210) includes a computing device configured to perform at least some of the steps described with reference to the flowchart of FIG. 8, and one or more communication interfaces that enable the hub to interface with one or more access points (112), the cloud (230), and the computing device that executes the user application (250). The computing device of the hub may be, for example, an embedded system that includes all components of the computing device on a single printed circuit board (PCB), or a system on a chip (SOC), i.e., an integrated circuit (IC) that integrates all components of the computing device into a single chip. The computing device may include one or more processor cores, associated memory (e.g., random access memory (RAM), cache memory, flash memory, etc.), one or more network interfaces (e.g., an Ethernet interface, a Wi-Fi interface, a Bluetooth interface, etc.), and interfaces to storage devices, input and output devices, etc. The computing device may further include one or more storage device(s) (e.g., a hard disk, an optical drive such as a compact disk (CD) drive or digital versatile disk (DVD) drive, flash memory, etc.), and numerous other elements and functionalities. In one embodiment of the invention, the computing device includes an operating system that may include functionality to execute the methods further described below. Those skilled in the art will appreciate that the invention is not limited to the aforementioned configuration of the computing device.

The cloud (230), in accordance with one or more embodiments of the invention, may be formed by multiple/many networked computing devices. These computing devices may be geographically and organizationally distributed in any way. For example, some of these computing devices may be located in a data center, whereas other such computing devices may be individual physical or virtual servers. An exemplary computing system, as it may be used in the cloud, is shown in FIG. 7. One or more of the computing devices may host the hub/cloud platform (270), analogous to how the hub/cloud platform is hosted on the hub (210). While the components of the hub/cloud platform that are executing on the hub (210) and that are executing on a computing device in the cloud (230) may operate separately, they are interconnected, e.g. via the backhaul link (140), thus enabling synchronization between these components. Accordingly, the same information may be available, regardless of whether the user application connects via the hub (210) or via the cloud (230). Temporary discrepancies may exist though, e.g., during times when the backhaul link (140) is interrupted, and a synchronization is therefore unavailable. Further, because additional, e.g., more complex, data processing may be performed in the cloud, additional data, resulting from the additional processing, may be available when connecting to the hub/cloud platform (270) via the cloud. Such data may, however, also be available via the hub (210), if they are synchronized to the hub (210) via the backhaul link (140). The cloud may run multiple instances of the hub/cloud platform in order to support the load of many sites and/or many users. Depending on the configuration of the hub/cloud platform, incoming data, i.e., data received from a particular hub, a particular device, a particular site, or a particular customer, may be distributed between multiple instances, or may be consistently assigned to the same instance, using, e.g., a consistent hash ring configuration.

Those skilled in the art will recognize that other configurations that deviate from the configuration introduced in FIG. 2A may exist, without departing from the invention. For example, in monitoring systems (110) that do not include an interface to the cloud (230), the hub/cloud platform (270) may solely execute on the hub. In such a scenario, the hub is configured to “self-backhaul”, i.e., the hub may collect and consolidate monitoring device data and may perform some or even all of the processing that would otherwise be performed in the cloud. Similarly, in monitoring systems in which the access points (112) directly interface with the cloud (230), the hub/cloud platform (270) may solely execute in the cloud. All functionality, even functionally that would typically be provided by the hub, in this case may be provided in the cloud. The configuration of the monitoring system, with or without hub, in one or more embodiments of the invention, may be transparent, i.e., monitoring devices or other devices may operate in the same manner, regardless of the presence of a hub. Similarly, a user may experience the same monitoring system, whether the hub is present or not.

Turning to FIG. 2B, additional details of the hub/cloud platform (270) are shown. In one or more embodiments of the invention, the hub-cloud platform is organized in layers. Core services (276) provide basic functionalities such as data storage, network, and messaging. On top of the core services (276), the IoT services (274) provide services that are specific to IoT networks, but that are not necessarily specific to a particular application, such as the use in a healthcare environment. The IoT services may thus include, for example, location services (e.g., GPS, TDOA or RSSI based), IoT network services and configurations, etc. The topmost layer includes application and/or environment-specific services (272). These services, in case of a healthcare environment may include, for example, analysis of patients' vital signs, a patient location tracking interface, etc. In contrast, in case of an oilfield environment, these services may include, pipeline operation analytics. Additional application-specific layers may be added, without departing from the invention. The hub/cloud platform is, thus, modular, allowing adaptation to many applications, depending on the services selected for execution on the hub/cloud platform.

These services, in accordance with one or more embodiments of the invention, may be available through the hub (210) and/or through the cloud (230). A synchronization may be performed between the services executing in the cloud and the services executing on the hub, thus maintaining consistency between the hub and the cloud. As long as a communication link (e.g., the backhaul link (140)) is available, the data available through the hub and through the cloud may be identical. However, if the communication link temporarily becomes unavailable, data that is accumulated on the hub may not be available through the cloud. A synchronization may be performed once the communication link is restored, to update the cloud with the data available on the hub. Accordingly, a consistent data view is available via hub and cloud, in accordance with one or more embodiments of the invention.

Turning to FIGS. 3A and 3B, access points (300), in accordance with one or more embodiments of the invention, are shown. In FIG. 3A, the general design of an exemplary access point is shown, and in FIG. 3B, the architecture of the access point is illustrated. The exemplary access point shown in FIG. 3A includes a broadband interface antenna (302), a GPS antenna (312), an IoT radio antenna (322) and solar cells (332). As shown in FIG. 3B, the access point further includes a broadband interface (304), a GPS interface (314) and an IoT radio interface (324).

The broadband interface (304) uses the broadband antenna (302) in order to send and receive broadband data transmissions when in contact with, e.g., other access points, as illustrated in FIG. 1B and/or with other devices such as smartphones, laptops, cameras and/or drones that are also equipped with broadband interfaces. The broadband interface may support mesh, point-to-point and multi-point connections. The broadband interface may be based on the Wi-Fi standard, using, e.g., the 2.4 and/or 5 GHz radio bands. Alternatively, the broadband interface may be a cellular data interface, e.g., a 3G or 4G/LTE or 5G interface, or any other wireless data interface, without departing from the invention.

The GPS interface (314) uses the GPS antenna (312) to obtain position signals from the global positioning system or from alternative satellite navigation services. The position signal enables the access point to accurately determine its own position. In one or more embodiments of the invention, the GPS interface further obtains an accurate time base that may be used by the access point to perform localization tasks using TDOA methods, as further described below.

The IoT radio interface (324) uses the IoT radio antenna (322) to communicate with one or more IoT devices such as the monitoring devices (104). The IoT interface may be based on a low power wide area network standard such as, for example, LoRa. The resulting narrowband link is particularly suitable for communications between the access point and the monitoring devices or other sensors, due to its low power requirements, long range, and its ability to interface with many monitoring devices and/or other devices. In one or more embodiments of the invention, the IoT radio interface (324) supports communication protocol extensions implemented on top of an existing IoT communication protocol to provide scheduled communications and timing beacons as further discussed below, with reference to FIG. 6.

In one or more embodiments of the invention, the access point (300) further includes an access point processing engine (342). The access point processing engine may handle the processing of data received from monitoring devices and other sensors, and may coordinate the uploading of the processed data to either the hub or to the cloud. The processing of data may involve, for example, data aggregation, data filtering, data fusion, data compression and/or data encryption.

In one or more embodiments of the invention, the access point (300) further includes a monitoring device localization engine (344). The monitoring device localization engine may be used to determine the locations of monitoring devices that are within the coverage region of the access point. The localization may be performed, for example, using TDOA methods. Using the TDOA method, triangulation, based on the differences in time delay of a data transmission by a monitoring device, received by at least three access points, may be performed. The monitoring device localization engine of an access point may use this time delay information to determine the location of the monitoring device responsible for the data transmission. Because TDOA methods depend on the availability of an accurate time base to the monitoring devices whose location is to be determined, communication protocol extensions that enable dissemination of an accurate time base to the monitoring devices via the IoT link, as discussed with reference to FIG. 6, are used by the access point. Alternatively, the monitoring device localization engine may extract the location of a monitoring device from a message provided by a sensor equipped with a GPS unit. Further, the monitoring device localization engine may also determine a location of a monitoring device based on the signal strength of a data transmission obtained from the monitoring device, using the RSSI method. Those skilled in the art will appreciate that, although the method performed by the monitoring device localization engine is described with regard to monitoring devices, any device that is equipped with an IoT interface, and that is capable to communicate with the access points, may be localized by the monitoring device localization engine.

The access point processing engine (342) and the monitoring device localization engine (344) may be software executing on a computing device (not shown) of the access point (300). The computing device of the hub may be, for example, an embedded system that includes all components of the computing device on a single printed circuit board (PCB), or a system on a chip (SOC), i.e., an integrated circuit (IC) that integrates all components of the computing device into a single chip. The computing device may include one or more processor cores, associated memory (e.g., random access memory (RAM), cache memory, flash memory, etc.), and interfaces to storage devices, input and output devices, etc. The computing device may further include one or more storage device(s) (e.g., a hard disk, an optical drive such as a compact disk (CD) drive or digital versatile disk (DVD) drive, flash memory, etc.), and numerous other elements and functionalities. In one embodiment of the invention, the computing device includes an operating system that may include functionality to execute the methods further described below. Those skilled in the art will appreciate that the invention is not limited to the aforementioned configuration of the computing device.

In one or more embodiments of the invention, the access point further includes a power system that may include the solar cells (332), a battery (334) and a charge controller (336), powering the access point. The battery may be deep-cycle capable to guarantee continued operation at night or under cloudy conditions when power provided by the solar cells is insufficient. The solar cells may be dimensioned to enable powering the access point while also recharging the battery. Alternatively, the access point may be powered externally, e.g., using power over Ethernet (PoE) or using a dedicated power input. The charge controller in combination with the access point processing engine (342) may provide charging, battery status and power consumption analytics, enabling power management of the access point. A direct current (DC) power and data over DC power link may be used to power the access point by the power system, but also to enable the charge controller to communicate status information (such as battery level, temperature, etc.) to the access point.

FIGS. 3C-3G show an exemplary access point & hub assembly, in which a hub and an access point are installed in combination on a pole. The assembly (390) includes the access point (300), an antenna pole (392), solar cells (332) and a hub & battery box (394). Alternatively, the access point & hub assembly may be powered by AC line voltage, either continuously or intermittently. In this case, the access point & hub assembly may not be equipped with solar cells, but may instead include AC to DC conversion circuits to power the access point & hub assembly and/or to charge the battery. While the access point (300) is installed near the top of the antenna pole (392), for improved reception, the hub (318) may be housed in the hub & battery box (394), together with the battery (334) and the charge controller (336) near the base of the antenna pole (392), thus facilitating access. The access point (300) may be connected to the hub (318), using an Ethernet cable, which may also power the access point using PoE. In one embodiment of the invention, the antenna pole (392) can be pivoted into a horizontal position, thereby facilitating installation and servicing of the access point (300) near the top of the antenna pole as illustrated in FIG. 3G

FIGS. 4A-4C show diagrams of a monitoring device of a system for monitoring assets, in accordance with one or more embodiments of the invention.

FIG. 4A shows a monitoring device (400) (herein may also be referred to a “IoT sensor”) in accordance with one or more embodiments of the invention that may be used in the monitoring system (110) described above in reference to FIGS. 1A-1H. The monitoring device (400) may be a sensor system that is used to monitor an asset, including the asset's location and other variables, as subsequently discussed. The monitoring device may be equipped with a mounting or attachment element that is application specific. For example, in industrial or commercial applications, the monitoring device may be permanently bolted to an equipment to be monitored. In animal and/or human applications, the monitoring device may be attached using an ear pin, a collar, and/or a dermal patch. Further, in human applications, the monitoring device may be designed as a wristband, an ankle monitor, a dermal patch, or as a unit that can be worn in a pocket. The monitoring device may further be installed on a hard hat, as it may be worn by workers in the oil & gas, construction, refining, and other industries. In such applications, the monitoring device may be a tag that is attached to the front or the back of a hard hat. In automotive applications, the monitoring device may be a tag that is hanging from the rear view mirror. If monitoring devices are used to track the location, temperature and/or fill level of portable tanks, such as propane tanks, these monitoring devices may be equipped with mounts to permanently or temporarily attach the monitoring devices to these tanks. Those skilled in the art will appreciate that the monitoring device is suitable for many applications and may thus be adapted to include mounting elements as needed. The monitoring device may further be equipped with an RFID tag (404). The REID tag (404) may electronically store information such as a unique asset-specific identifier. The tag may be passive, i.e., not requiring a battery, and may be electromagnetically powered by a nearby reader, e.g., the RFID wand (132), previously discussed in FIG. 1C. The monitoring device may further include one or more external sensors (406). Such sensors may be physiological sensors (e.g., blood pressure or heart rate sensors) or sensors for environmental variables such as temperature, humidity, etc. These sensors may have a wired or optical interface (e.g., infrared) to the monitoring device.

In one or more embodiments of the invention, the monitoring device (400) includes an IoT transceiver (410). The IoT transceiver (410) may be configured to communicate with one or more access points, using an IoT protocol such as LoRa. Communications may include, but are not limited to, the receiving of a time base from one or more access points, the receiving of a configuration, the receiving of a firmware, the sending of monitoring device data, e.g., data previously collected by one of the subsequently described sensors, and/or the sending of monitoring device status data, such as errors, battery level, etc. The activity of the IoT transceiver may be optimized to minimize power consumption. For example, the IoT transceiver may be in a deep sleep mode whenever no transmission of data is required.

In one or more embodiments of the invention, the monitoring device (400) further includes a processor (412). The processor may gather data from one or more of the subsequently described sensors and may process the data for transmission via the IoT transceiver. The transmissions may be performed as specified by the IoT communication protocol overlay, further described with reference to FIG. 6 to minimize communication inefficiencies such as collisions with data sent by other monitoring devices and/or to conserve battery power. The organization of the data as instructed by the IoT communication protocol overlay may be performed by the processor (412). The processor may be a microcontroller unit (MCU) that may be implemented as a system on a chip (SOC). The processor may be selected based on computational requirements and battery life requirements.

In one embodiment of the invention, the monitoring device (400) may include a GPS receiver (414), sensing devices (416) and/or a peripheral in-vivo transceiver (418). The GPS receiver, if present, may be used to determine the location of the asset when other, more power efficient, methods for determining the location (such as TDOA and/or RSSI) are not available, e.g., when the number of access points that are simultaneously in communication with the monitoring device is insufficient or the resulting location data is not sufficiently accurate. When not in use, the GPS receiver may be in a deep sleep mode or completely powered down. One or more sensing devices (416) may be used to obtain measurements from the monitored asset (102) or the surrounding environment. These sensing devices may include, but are not limited to, pressures sensors for gas and/or liquid applications, air or gas leak sensors, fill level sensors e.g., for storage tanks, valve position sensors (e.g., to monitor the function of valves), weight and/or strain sensors (including bending, torsion, etc.), and temperature sensors, spectroscopy sensors (to perform chemical analyses beyond basic gas sensing), energy usage or delivery sensors, etc. The one or more sensing devices (416) may be interfaced with the processor (412) using digital and/or analog interfaces. One example of the sensing device (416) may be, but is not limited to, an accelerometer.

In one or more embodiments of the invention, the monitoring device (400) is further equipped with a control interface (not shown). The control interface may include analog or digital outputs, including communication bus systems, and/or relays, motors, or any other equipment that may be used to control functions of the monitored asset (102) and/or other components in vicinity of the monitored asset. Those skilled in the art will appreciate that the control interface may be used to control any function of the monitored asset or functions of other components in the monitored environment.

The optionally present peripheral in-vivo sensor transceiver (418), in one embodiment of the invention, establishes a data link to one or more peripheral in-vivo type sensors, such as a the sensors discussed below, with reference to FIGS. 5A-5C. The data link may be very low power, limited to a range of only, for example, three to six feet. A transmission frequency may be in a range suitable to penetrate tissue. Highly power efficient circuits (such as class C amplification) may be used to minimize power consumption, in particular on the side of the in-vivo sensor, which may need to operate using small batteries. The data link may use a communication protocol analogous to the protocol further described below with reference to FIG. 6, although a simplified version (e.g., fewer communication slots) may be provided.

In one or more embodiments of the invention, the components of the monitoring device are battery powered. The battery (424) may be a rechargeable or a non-rechargeable battery that may or not be replaceable, selected to power the components of the monitoring device for a specified duration, e.g., for multiple months or years. If the battery is rechargeable, a power or charge controller (426) may control the charging of the battery, e.g., from solar cells (422) or other external power sources, such as inductively provided power. The power/charge controller may further communicate battery status information to the processor (412). This status information may be communicated to an access point, e.g., when a low battery level is detected. In addition, the battery level may directly govern the operation of the monitoring device. For example, when a low battery level is detected, the communication frequency may be reduced, certain sensors may be deactivated, etc. External power supplies may be used, e.g., if the monitoring device is stationary.

FIGS. 4B and 4C show an exemplary design of the monitoring device (400) as a tag sensor system (herein referred to as “tag sensor”) for ranching applications. The tag sensor may be used to monitor an animal, including the animal's location and other variables, as subsequently discussed. The tag sensor may be equipped with a fastener such as an ear pin (402) that allows the tag sensor to remain attached to the animal for a prolonged time, up to multiple years. Other designs may not include an ear pin. For example, alternatively, the tag may be integrated in a collar worn by the animal. The tag sensor may further include active components, including one or more external sensors (406). In one or more embodiments, the external sensors (406) may also be embedded within the tag sensor (i.e., the monitoring device (400)) as an internal sensor. Data from these sensors may be transmitted to one or more of the previously introduced access points using an IoT link. The external sensors (406) may be physiological sensors that may have a wired or optical interface (e.g., infrared) to the tag sensor. Sensors may include, but are not limited to animal temperature (via ear canal, e.g.), ambient temperature, pulse rate and blood pressure sensors that are able to monitor a physiological status of the animal. The animal temperature may be obtained using, for example, a temperature probe inserted into an animal's ear canal. The ambient temperature may be obtained using, for example, the temperature sensor of the processor (412), or a dedicated temperature sensor. Further, heart rate and/or blood pressure may be assessed using LED light sources and photo sensors. Additionally or alternatively, other types of sensors may be integrated in a tag sensor (400). Any sensor that can be interfaced with the processor (412) using an analog or digital interface may be added to the tag sensor.

FIGS. 5A-5C show diagrams of peripheral sensor systems, in accordance with one or more embodiments.

FIG. 5A shows a general peripheral system (500) (herein may also be referred to as “in-vivo sensor” and “peripheral sensor”). The peripheral sensor (500) may be one or more sensors used to monitor a living asset, including the asset's location and other variables, as subsequently discussed, and may be used in combination with the monitoring device (400) in the monitoring system (110) described above in reference to FIGS. 1A-IH and 4A-4C. The peripheral sensor (500) may include a sensing instrumentation (502), electronic circuits (510), and a battery (532). Depending on the environment for which the peripheral sensor (500) is designed, the peripheral sensor may be hermetically sealed e.g. to prevent fluids from entering the sensor. The sensing instrumentation may include, but is not limited to, pressures sensors for gas and/or liquid applications, air or gas leak sensors, fill level sensors e.g., for storage tanks, valve position sensors (e.g., to monitor the function of valves), weight and/or strain sensors (including bending, torsion, etc.), and temperature sensors, spectroscopy sensors (to perform chemical analyses beyond basic gas sensing), energy usage or delivery sensors, etc. Consider, for example, the application of monitoring devices and peripheral sensors in mining, refining or industrial environments. The peripheral sensors may include gas sensors, configured to provide early hazard warnings to workers, on an individual basis. Alternatively, in another scenario, a monitoring device is used to monitor the fill level of a storage tank. A peripheral sensor, interfacing with the monitoring device, may further monitor a pump to monitor vibration, energy consumption, including static and transient energy consumption, and/or to control the pump, and thus, indirectly, the fill level of the storage tank. Those skilled in the art will appreciate that the peripheral sensor, when equipped with a control interface, may be used to control any function of the monitored asset or functions of other components in the monitored environment.

The electronic circuits (510), in accordance with one or more embodiments of the invention, includes a processor (504) and a peripheral sensor transceiver (506). The processor (504) may be a particularly energy-efficient unit such as a microcontroller that may be implemented as a system on a chip (SOC). The processor may be selected based on computational requirements and battery life requirements. Temporarily used peripheral sensors may only need to remain operative for a few days, whereas permanently installed versions of the peripheral sensor may need to be operational for the lifetime of the monitored living asset. The peripheral sensor transceiver (506) is configured to interface the peripheral sensor with the monitoring device (400) over a short distance using a low-power signal with minimal power requirements, in order to communicate the collected peripheral data to the monitoring device, from where it may be forwarded to an access point.

The battery (532) may be a rechargeable or a non-rechargeable battery, selected to power the components of the peripheral sensor for a specified duration, ranging from a few days to the lifetime of the asset. If the battery is rechargeable, a power controller (534) may control the charging of the battery from inductively provided power. The power controller may further communicate battery status information to the processor (504). This status information may be communicated to an access point, e.g., when a low battery level is detected. In addition, the battery level may directly govern the operation of the peripheral sensor. For example, when a low battery level is detected, the communication frequency may be reduced, certain sensors may be deactivated, etc.

FIG. 5B shows one example of the peripheral sensor (500). Specifically, in one or more embodiments, the peripheral sensor (500) may be an in-vive sensing capsule sensor system. The in-vivo sensing capsule sensor system may further include an antenna (522) that is connected to the peripheral sensor transceiver (506). The peripheral sensor (500) may be an implanted capsule (e.g., a capsule that was subcutaneously injected) or an ingested capsule that is passing the digestive tract and may be used to collect physiological data. The capsule may be made from, for example, plastic, epoxy, ceramics or glass. The sensing instrumentation (502) may be a temperature sensor, a heart rate sensor, a blood pressure sensor, etc that is able to collect physiological data from the living asset.

FIG. 5C shows one example of the peripheral sensor (500). Specifically, in one or more embodiments, the peripheral sensor (500) may be an in-vivo dermal patch sensor system. The in-vivo dermal patch sensor system may include all of the internal and/or external sensing instrumentation (502), the electronic circuits (510), the antenna (522), and the battery (532) included in the in-vivo sensing capsule embedded within and/or disposed on the surface of the dermal patch sensor. The peripheral sensor (500) may be an implanted dermal patch (e.g., a skin patch and/or a medicated adhesive patch that is placed on the skin to deliver medication into the skin) that is attached to a surface (e.g., the skin) of an asset, and may be used to collect physiological data from the asset. The dermal patch may be made from, for example, medical-grade hypo allergenic sealed plastic materials and flexible surgical latex materials. For example, the dermal patch may be a surgical latex patch and/or bandage. In one or more embodiments, the internal and/or external sensing instrumentation (502), the electronic circuits (510), the antenna (522), and the battery (532) may be encapsulated with stainless steel and embedded within the material of the dermal patch.

The sensing instrumentation (502) may be a temperature sensor, a heart rate sensor, a blood pressure sensor, etc that is able to collect physiological data from the asset. In one or more embodiments, the battery (532) may be rechargeable and the dermal patch sensor system may include the power or charge controller (not shown) and solar cells (not shown) of the monitoring device as described above in reference to FIGS. 4A-4C. The solar cells may be provided as a flexible solar panel that is disposed on a surface of the dermal patch sensor that faces away from the surface (e.g., the skin) of the asset to be exposed to direct sunlight.

Turning to FIG. 6, an IoT communication protocol overlay, in accordance with one or more embodiments of the invention, is shown. The IoT communication protocol overlay is designed to enable the distribution of an accurate time base by an access point to monitoring devices or other devices communicating with the access point. The IoT communication protocol overlay further establishes rules for data exchanges in the form of frequency bands and time slots to be used for communications, to reduce or eliminate collisions that may otherwise occur when multiple monitoring devices attempt to simultaneously transmit data. In one or more embodiments of the invention, the IoT communication protocol overlay may be used to extend existing IoT protocols such as LoRa or SigFox, but also other protocols such as the 802.11 Wi-Fi protocol. FIG. 6 shows an IoT communication protocol overlay (600) in which a superframe (602) and frames (604) are established. The beginning of each frame is marked by a beacon (612), emitted by the access point. A beacon may include or may be followed by a communication of various data to the IoT devices within the range of the access point. The data may include a precise time base that the access point may have obtained from its GPS unit. The data may further include a specification of the IoT communication protocol overlay, thus informing the IoT devices that are supposed to communicate with the access point of the timing and frequency of time slots assigned to them for data transmission.

The beacon may then be followed by transmissions of sensor data in the communication slots (616). Each communication slot may be of a fixed duration and may be located at a set frequency. In the exemplary IoT communication protocol overlay (600) of FIG. 6, a frame includes 24 communication slots. Groups of 8 communication slots may be simultaneously transmitted using different frequencies. Communication slots may be assigned in any way. For example, a communication by a particular IoT device may be performed using a single assigned communication slot or, if necessary, multiple communication slots that may occur in parallel at different frequencies (channels) and/or subsequently. No communication slot may be assigned to multiple devices to prevent communication collisions. A frame (×04) ends with a beacon guard time (×14), during which no communications by any of the IoT devices that rely on the IoT communication protocol overlay may be allowed. However, other IoT devices that are merely capable of communicating using the underlying IoT communication protocol, but not the IoT communication protocol overlay, may communicate during the beacon guard time.

In total, the IoT communication protocol overlay (600) provides 72 communication slots (616). Accordingly, up to 72 individual communications may be performed in a single superframe (602). If these 72 communications are insufficient to serve all IoT devices, the protocol overlay may be modified in various ways without departing from the invention. For example, a superframe may be configured to include more than three frames. Additionally or alternatively, a frame may include more than three consecutive communication slots, and/or additional frequencies (channels) may be used to allow simultaneous transmission of additional communication slots. The same IoT communication protocol overlay may be used by all access points across a site.

In one or more embodiments of the invention, not all channels that are available in the underlying IoT communication protocol are used by the IoT communication protocol overlay. Channels that are not made available may be used to support devices that are not designed to work with the IoT communication protocol overlay, while being able to use the underlying IoT protocols. Such channels may also be used for lengthy transmissions such as a firmware provided over the air.

FIG. 7 shows a flowchart describing methods for monitoring assets, in accordance with one or more embodiments of the invention. The method may be used, for example, to track the location of persons or equipment and/or physiological signals of tracked individuals. The method may be executed repeatedly over time, thus enabling a user to continuously monitor the assets and to detect changes, e.g., when the assets move, when their state changes or environmental conditions change, etc.

In Step 700, monitoring data is collected from the assets that are equipped with monitoring devices. Data may be collected from the various sensors of a monitoring device, but also from peripheral sensors, if peripheral sensors are used. The collection may occur as scheduled, e.g., based on the time-base provided by the IoT communication protocol overlay or spontaneously, e.g., upon request or when a particular event is detected. The data collection by one monitoring device may be independent from the data collection by other monitoring devices. The collected data may be buffered by the monitoring device until it can be transmitted to an access point.

In Step 702, the monitoring devices provide the collected data to one or more access points, using the IoT link. Each monitoring device uses a communication slot at a particular time and in a particular frequency band, as specified by the IoT communication protocol overlay, thus avoiding transmission interference by multiple monitoring devices using the same communication slot. The transmissions of the monitoring devices may be received by one or more access points within range.

In Step 704, the received data may be processed by the access point(s) that received the data. The processing may include aggregating, filtering, fusing, compressing and/or encrypting the data. The processing may further include the exchange of data with other access points. For example, TDOA data may be exchanged between access points to determine a location of a tag sensor, relative to the access points.

In Step 706, the processed data are provided to a hub, using the broadband link that interfaces the access point(s) and the hub. Step 806 is optional and is executed only if a hub exists in the used system configuration. If no hub exists, the processed data may alternatively be provided to the cloud. Regardless of whether the system is configured to use a hub, a cloud or both, the processed data is received by the hub/cloud platform which is executing on the hub, in the cloud, or on the hub and in the cloud.

In Step 708, data analytics are performed by the hub/cloud platform executing on the hub. The data analytics may include modules that are generic to a variety of applications such as location tracking, and other modules that are specific to a particular application, such as equipment tracking in the oil & gas industry, monitoring physiological parameters of patients, etc. The data analytics may additionally or alternatively be performed in the cloud.

In Step 710, the processed monitoring data is uploaded to the cloud. This step may be performed in systems that include a cloud environment and in systems that include a combination of the hub and the cloud. Accordingly, data obtained from the tag sensors may be equally accessible via the cloud and via the hub.

In Step 712, a user is provided access to the processed monitoring data using the hub/cloud platform that is executing on the hub, in the cloud, or on the hub and in the cloud. The user may access the processed monitoring data using any type of computing device that is capable of interfacing with the hub/cloud platform. The user may obtain a visualization of the processed monitoring data, which may include text, graphics, charts, etc. The user may access a time history of the processed monitoring data and may further also access the unprocessed or partially processed data obtained from the tag sensors. Alerts may be provided to the user under certain configurable conditions. For example, an alert may be provided if a tracked equipment is leaving a particular area such as a parking lot, if unusual movement patterns (such as the lack of movement of an elderly patient, indicating a potential problem) are detected, or if physiological measurements are beyond a specified range.

FIG. 8 shows a flowchart of a monitoring device transmission protocol for the monitoring device of FIGS. 4A-4C, in accordance with one or more embodiments. In one or more embodiments, the method as shown in FIG. 8 is a computer-implemented method that may implemented by the processor of the monitoring device described above in reference to FIGS. 4A-4C. In one or more embodiments, the monitoring device transmission protocol of FIG. 8 may be employed with the method for monitoring assets as described above in reference to FIG. 7.

In STEP 805, a determination is made to determine if the current time of day is daytime. In one or more embodiments, a monitoring frequency of the monitoring device may be adjusted based on the time of day. In times of high activity (i.e., daytime) the monitoring device may be configured with a higher monitoring frequency than a time of low activity (i.e., night time). For example, assume that the environment is a ranch and assume that asset being monitored is livestock. Further assume that the waking hours of the cattle being monitored is set as “daytime” and the resting hours of the cattle being monitored is set as “nighttime”. During daytime hours, the monitoring device may be configured, as described below, with a high monitoring frequency to be able to accurately monitor the full activity of the active cattle. During night time hours, a lower monitoring frequency is needed and the monitoring device may also be switched into a passive mode (i.e., sleep mode) as the cattle become less active, which also allows the monitoring device to conserve power.

In the event that the determination in STEP 805 is YES, the process proceeds to STEP 810 where the monitoring device measures and transmits to an access point of an IoT system a first set of sensing data in a first predetermined time slot.

In STEP 815, the monitoring device measures and transmits to the access point of the IoT system a third set of sensing data in a third predetermined time slot.

In STEP 820, the monitoring device measures and transmits to the access point of the IoT system a third set of sensing data in a third predetermined time slot.

In one or more embodiments, the first, second, and third predetermined time slot may be any time-based value (e.g., seconds, minutes, hours, etc.) and may also be set to a same value. For example, the first, second, and third predetermined time slots may all be ten minutes.

In one or more embodiments, the STEPs 810, 815, 820 may be executed as sequence that is repeated every N minutes. The value of N may be set based on a frequency of activity established for the asset and/or the battery life of the monitoring device. For example, N=30. The first, second, and third set of sensing data may include any location (e.g., GPS, TDoA, RSSI), environmental, and/or physiological sensing data captured by the monitoring device and/or any physiological sensing data transmitted from a peripheral sensor to the monitoring device. The data included sets of sensing data may be different in each of STEP 810, 815, and 820 and may be altered based on the battery life of the monitoring device.

In one or more embodiments, the sequence described in STEPs 810 to 820 may include more than three transmission steps as described. The number of transmission steps may be adjusted based on the frequency of activity established for the asset and/or the battery life of the monitoring device.

In the event that the determination in STEP 805 is NO, the process proceeds to STEP 825 where the monitoring device measures and transmits, in a first active time slot, the first set of sensing data to the access point of IoT system in a first active time slot. Once of the transmission of the first set of sensing data is complete, the monitoring device enters a rest mode and initiates an internal counter to wake up and perform a synchronization in STEP 830.

In STEP 830, once the monitoring device wakes up upon expiration of the internal counter, the monitoring device, listens for an IoT access point beacon transmission and synchronizes with the IoT access point in a first set of passive time slots. In one or more embodiments, upon receiving the transmission beacon from the IoT access point, the monitoring device resynchronizes with the IoT access point.

In STEP 835, once the monitoring device has resynchronized with the IoT access point, the monitoring device measures and transmits, in a second active time slot, the second set of sensing data to the access point of IoT system in a second active time slot. Once of the transmission of the second set of sensing data is complete, the monitoring device enters the rest mode and initiates the internal counter to wake up and perform the synchronization in STEP 840.

In STEP 840, once the monitoring device wakes up upon expiration of the internal counter, the monitoring device, listens for the IoT access point beacon transmission and synchronizes with the IoT access point in a second set of passive time slots. In one or more embodiments, upon receiving the transmission beacon from the IoT access point, the monitoring device resynchronizes with the IoT access point.

In STEP 845, once the monitoring device has resynchronized with the IoT access point, the monitoring device measures and transmits, in a third active time slot, the third set of sensing data to the access point of IoT system in a third active time slot. Once of the transmission of the third set of sensing data is complete, the monitoring device enters the rest mode and initiates the internal counter to wake up and perform the synchronization in STEP 850.

In STEP 850, once the monitoring device wakes up upon expiration of the internal counter, the monitoring device, listens for the IoT access point beacon transmission and synchronizes with the IoT access point in a third set of passive timeslots. In one or more embodiments, upon receiving the transmission beacon from the IoT access point, the monitoring device resynchronizes with the IoT access point.

In one or more embodiments, the first, second, and third active time slots may be any time-based value (e.g., seconds, minutes, hours, etc.) and may also be set to a same value. For example, the first, second, and third active time slots may all be ten minutes. Similarly, the first, second, and third passive time slots may be any time-based value (e.g., seconds, minutes, hours, etc.) and may also be set to a same value. For example, the first, second, and third passive time slots may all be ten minutes.

In one or more embodiments, the STEP 835 through STEP 850 may be executed as sequence that is repeated every M minutes. The value of M may be set based on the frequency of activity established for the asset and/or the battery life of the monitoring device. For example, M=90. Similar to STEPs 810 to 820, the first, second, and third set of sensing data may include any location (e.g., GPS, TDoA, RSSI), environmental, and/or physiological sensing data captured by the monitoring device and/or any physiological sensing data transmitted from a peripheral sensor to the monitoring device. The data included sets of sensing data may be different in each of STEP 825, 835, and 845 and may be altered based on the battery life of the monitoring device.

In one or more embodiments, by entering the rest mode, the monitoring device is able to conserve battery life during a time (i.e., the passive time slots) where measuring and transmission of sensing data is not required as determined by the frequency of activity established for the asset and/or the battery life of the monitoring device.

In one or more embodiments, the sequence described in STEPs 825 to 830 may include more than three pairs of transmission and synchronization steps as described. The number of transmission and synchronization pairs may be adjusted based on the frequency of activity established for the asset and/or the battery life of the monitoring device.

FIG. 9 shows a sensor protocol diagram, in accordance with one or more embodiments. In one or more embodiments, the sensor protocol diagram is a communication and synchronization method employed by the monitoring device, one or more peripheral sensors associated with the monitoring device, and an access point in an IoT system. The monitoring device, the peripheral sensor, and the access point have been described above in reference to FIGS. 3-5.

In one or more embodiments, and as discussed above in reference to the IoT communication protocol of FIG. 6, the IoT access point transmits an IoT Access Point Super Frame Beacon (903). At this point, the monitoring device and the peripheral sensor have been activated and associated with the IoT system.

In one or more embodiments, the IoT Access Point Frame Beacon (905) is a beacon signal transmitted by the IoT access point that allows the monitoring device to synchronize with the IoT access point when the IoT Access Point Frame Beacon (905) is received by the monitoring device. Once synchronized with the access point, the monitoring device is able to transmit a set of sensing data, as described above in reference with FIGS. 4 and 8, to the access point within the Monitoring Device Transmit Slot (907).

In one or more embodiments, the Monitoring Device Peripheral Beacon (909) is a beacon signal transmitted by the monitoring device that allows the one or more peripheral sensors to synchronize with the monitoring device when the Monitoring Device Peripheral Beacon (909) is received by one or more of the peripheral sensors. Once synchronized with the access point, the one or more peripheral sensors are able to transmit a set of sensing data, as described above in reference with FIG. 5, to the monitoring device within the Peripheral Sensor Transmit Slot (913) that may be transferred in any one or more of the Possible Peripheral Sensor Transmit Slots (911).

In one or more embodiments, the peripheral sensor may be configured to use different modulation schemes such as frequency shift key (FSK) or minimum shift key (MSK) at frequency of operation that does not interfere with a frequency of operation utilized by the monitoring device. For example, the frequency of operation of the peripheral sensor may be between 250 MHz to 900 MHz.

FIG. 10 shows an example flowchart of sensing data transmission using the IoT sensor protocol diagram of FIG. 9, in accordance to one or more embodiments. In one or more embodiments, the method as shown in FIG. 10 is a computer-implemented method that may implemented by the processors of the monitoring device and the peripheral sensors described above in reference to FIGS. 4A-4C and 5A-5B. The steps described in the flowchart of FIG. 10 are described in viewpoint of only a single peripheral sensor being associated with the monitoring device. However, in one or more embodiments, the monitoring device may be associated with more than one peripheral sensors (i.e., 1 to X number of peripheral sensors where X can be any integer greater than 1).

In STEP 1005, a determination is made to determine if the monitoring device and peripheral sensor are activated and associated to an IoT system.

In the event that the determination in STEP 1005 is NO, the monitoring device and the peripheral sensor are activated and associated with the IoT system. In one or more embodiments, the correlation of the monitoring device and the peripheral sensors within the IoT system may be described with respect to the following association tree:

-   -   An IoT system that includes one or more access points that are         each coupled with one or more monitoring devices and         communicates with the monitoring devices via an IoT link.     -   Each monitoring device is assigned, as described above in         reference to FIG. 9, a monitoring device transmit slot to         communicate with the respective access points.     -   Each monitoring device is configured to act as a local access         point for one or more of the peripheral sensors that are each         given, as described above in FIG. 9, peripheral sensor transmit         slots to transmit sensing data to the monitoring device.

The activation and association of the peripheral sensor to the monitoring device will be described below in more detail with reference to FIG. 11.

In the event that the determination in STEP 1005 is YES, the process proceeds directly to STEP 1020 where the monitoring device and the peripheral sensor begin respective measurements to capture one or more sensing data.

In STEP 1025, the monitoring device transmits a peripheral sensor synchronization beacon for the peripheral sensor to synchronize with the monitoring device.

In STEP 1030, upon receiving the peripheral sensor synchronization beacon from the monitoring device, the peripheral sensor transmits one or more sensing data to the monitoring device and enters a deep sleep mode (i.e., a rest mode). Upon entering the deep sleep mode the peripheral sensor initiates an internal counter to wake up and perform a re-synchronization with the monitoring device upon expiration of the internal counter. In one or more embodiments, the sensing data transmitted by the peripheral sensor includes a header that includes synchronization data for synchronizing with the associated monitoring device and one or more packet slots of variable sizes that includes one or more sensing data.

In STEP 1035, the monitoring device formats the sensing data received by from the peripheral sensor and merges the formatted sensing data with the sensing data collected (i.e., measured) by the monitoring device. In one or more embodiments, the formatted sensing data transmitted by the monitoring device includes a header with synchronization data for synchronization with the associated access point and one or more packet slots of variable sizes that includes one or more sensing data of the monitoring device and one or more sensing data received from the peripheral sensor.

In STEP 1040, upon synchronizing with an access point of the IoT system after receiving a monitoring device synchronization beacon from the access point, the monitoring device transmits the merged sensing data to the access point. In one or more embodiments, the monitoring device may enter into the deep sleep mode (i.e., a rest mode) after the merged data has been transmitted. Upon entering the deep sleep mode the monitoring device initiates an internal counter to wake up and perform a re-synchronization with the access point and peripheral sensor.

FIG. 11 shows a flowchart of an in-vivo sensor activation protocol, in accordance to one or more embodiments. In one or more embodiments, the method as shown in FIG. 11 is a computer-implemented method that may implemented by the processors of the peripheral sensors described above in reference to FIGS. 5A-5B. The steps described in the flowchart of FIG. 10 are described in viewpoint of only a single peripheral sensor. However, in one or more embodiments, a single monitoring device may be associated with more than one peripheral sensors (i.e., 1 to X number of peripheral sensors where X can be any integer greater than 1).

In STEP 1110, a peripheral sensor is initialized and activated. The peripheral sensor is removed from the original factory packaging and turned on (i.e., powered up). Upon activation, identifier data associated with the peripheral sensor (e.g., a device address, a unique device ID, a unique device key, etc.) is entered into the IoT system back end system in order for the devices already associated with the IoT system to be able to identify the activated peripheral sensor.

In STEP 1115, the initialized and activated peripheral sensor receives, from a monitoring device already associated with the IoT system, a synchronization beacon that includes a command with a join message. In one or more embodiments, the monitoring device transmits the synchronization beacon transmitted to the peripheral sensor after receiving a command from the IoT system when the IoT system receives a request to join the system from the initialized and activated peripheral sensor. In one or more embodiments the command may be a series of operations, administration, management, and provisioning (OAM&P) messages.

In STEP 1120, a determination is made by the peripheral sensor if the join message includes identifier data that matches with the identifier data of the peripheral sensor. In one or more embodiments, to ensure accuracy, the determination in STEP 1120 is performed for at least two synchronization beacons received from the monitoring device.

In the event that the determination in STEP 1120 is NO, the process returns to STEP 1115 and the peripheral sensor continuously listens for a synchronization beacon from a monitoring device associated with the IoT system that includes a join message with the identifier that matches with the identifier data of the peripheral sensor (i.e., STEPs 1115 and 1120 are repeated until the peripheral sensor received a synchronization beacon with a join message that includes identifier data that matches with the identifier data of the peripheral sensor).

In the event that the determination in STEP 1120 is YES, the process proceeds to STEP 1125 where the peripheral sensor transmits a join request message that includes the identifier data of the peripheral sensor to the monitoring device that transmitted the synchronization beacon. In one or more embodiments, the identifier data of the peripheral sensor transmitted in STEP 1125 may include the peripheral sensor device address and device key.

In STEP 1130, the peripheral sensor receives a join confirmation message from the monitoring device and the peripheral sensor is now associated with that respective monitoring device in the IoT system. In one or more embodiments, the join confirmation message is repeatedly sent, using a synchronization beacon, by the monitoring device to ensure that the join confirmation message is received by the peripheral sensor.

In one or more embodiments, the peripheral sensor may also be removed from an associated monitoring device through a removal and/or deactivation message received from the associated monitoring device. A deactivated peripheral sensor must be extracted and physically turned back on (i.e., powered up) in order to be renewed (i.e., renewed) for operation. The peripheral sensors associated with the monitoring may be removed when the associated monitoring device needs to be replaced due to damage, low battery, upgrade, etc. The removed peripheral sensors would then search for a new monitoring device on in the IoT system and initiates the activation protocol described above to be associated with the new monitoring device.

FIG. 12 shows a computing system in accordance with one or more embodiments of the invention. Embodiments of the invention may be implemented on a computing system. Any combination of mobile, desktop, server, embedded, or other types of hardware may be used. For example, as shown in FIG. 12, the computing system (1200) may include one or more computer processor(s) (1202), associated memory (1304) (e.g., random access memory (RAM), cache memory, flash memory, etc.), one or more storage device(s) (1206) (e.g., a hard disk, an optical drive such as a compact disk (CD) drive or digital versatile disk (DVD) drive, a flash memory stick, etc.), and numerous other elements and functionalities. The computer processor(s) (1202) may be an integrated circuit for processing instructions. For example, the computer processor(s) may be one or more cores, or micro-cores of a processor. The computing system (1200) may also include one or more input device(s) (1210), such as a touchscreen, keyboard, mouse, microphone, touchpad, electronic pen, or any other type of input device. Further, the computing system (1200) may include one or more output device(s) (1208), such as a screen (e.g., a liquid crystal display (LCD), a plasma display, touchscreen, cathode ray tube (CRT) monitor, projector, or other display device), a printer, external storage, or any other output device. One or more of the output device(s) may be the same or different from the input device(s). The computing system (1200) may be connected to a network (1212) (e.g., a local area network (LAN), a wide area network (WAN) such as the Internet, mobile network, or any other type of network) via a network interface connection (not shown). The input and output device(s) may be locally or remotely (e.g., via the network (1212)) connected to the computer processor(s) (1202), memory (1204), and storage device(s) (1206). Many different types of computing systems exist, and the aforementioned input and output device(s) may take other forms.

Software instructions in the form of computer readable program code to perform embodiments of the invention may be stored, in whole or in part, temporarily or permanently, on a non-transitory computer readable medium such as a CD, DVD, storage device, a diskette, a tape, flash memory, physical memory, or any other computer readable storage medium. Specifically, the software instructions may correspond to computer readable program code that, when executed by a processor(s), is configured to perform embodiments of the invention.

Further, one or more elements of the aforementioned computing system (1200) may be located at a remote location and connected to the other elements over a network (1212). Further, embodiments of the invention may be implemented on a distributed system having a plurality of nodes, where each portion of the invention may be located on a different node within the distributed system. In one embodiment of the invention, the node corresponds to a distinct computing device. Alternatively, the node may correspond to a computer processor with associated physical memory. The node may alternatively correspond to a computer processor or micro-core of a computer processor with shared memory and/or resources.

Various embodiments of the invention have one or more of the following advantages. Embodiments of the invention enable comprehensive monitoring of physical assets. The monitoring may include monitoring of asset location and numerous other measurements obtained from the asset or the environment surrounding the asset. The coverage provided by the monitoring system, in accordance with one or more embodiments of the invention, is scalable, from small spaces to tens of thousands of acres. The number of assets being monitored by the monitoring system, in accordance with one or more embodiments of the invention, is scalable, e.g., from a few assets to hundreds of thousands of assets in indoor, outdoor or mixed environments. Further, depending on the nature of the assets to be monitored, different monitoring devices may be relied upon. These monitoring devices are suitable for the monitoring of stationary and moving assets, equipment, goods, animals, humans, etc. Various components of the monitoring system may be operated on battery and/or solar power, with no access to the power grid and under hostile conditions including, but not limited to broad temperature ranges, wind, rain, dust, insects and mechanical stress, in accordance with one or more embodiments of the invention. Monitoring systems, in accordance with one or more embodiments of the invention, may be operated in environments that offer hardwired, wireless or no broadband Internet access.

The following use case scenarios are intended to provide examples of possible applications of the system for monitoring physical assets, in accordance with one or more embodiments of the invention. The use case scenarios are for illustrative purposes only, and the system for monitoring physical assets is not limited to the applications discussed below.

Use Case I: Oil & Gas Industry

In one embodiment of the invention, the monitoring system is used in the oil and/or gas industry. Non-stationary equipment, such as vehicles, may be tracked using monitoring devices, thus allowing monitoring location and appropriate use at any time. Further, stationary equipment, such as pumps, pipelines, storage tanks, etc., may also be monitored and/or controlled using monitoring devices. For example, monitoring devices equipped with appropriate sensors may measure flow, pressure, the presence of gasses, fill level, temperature, etc. In addition, monitoring devices may be used to remotely control equipment. For example, pumps may be remotely activated and deactivated, their power level may be adjusted, valves may be opened or closed, lights may be turned on and off, etc. The monitoring system, thus, facilitates smooth operation and productivity in the oil and/or gas industry.

Use Case II: Healthcare

In one embodiment of the invention, the monitoring system is used in healthcare. Patients' locations may be tracked using monitoring devices, which may be advantageous when monitoring elderly patients, patients with behavioral problems and/or patients suffering from memory loss, loss of orientation, etc. Further, the monitoring devices and/or peripheral sensors interfacing with the monitoring devices may also be used to obtain physiological parameters from patients. These physiological parameters may include, but are not limited to, heart rate, blood pressure, blood sugar, body temperature, movement patterns, etc. The monitoring system thus helps ensuring the wellbeing of patients

Use Case III: Vehicle Dealerships, Rental Car Agencies

In one embodiment of the invention, the monitoring system is used to track vehicles of vehicle dealers and/or rental car agencies. Numerous vehicles may be kept in large lots, and these vehicles may be located and tracked at any time, using the monitoring system. Such tracking may discourage unauthorized vehicle use by employees, thereby reducing losses due to use, wear and accidents. In addition, vehicles may also be tracked when taken on test drives by potential buyers, to ensure that these vehicles are not excessively used during the test drives. The monitoring system may thus facilitate operation of vehicle dealerships or rental car agencies and/or reduce cost.

Use Case IV: Campus Management & Security

In one embodiment of the invention, the monitoring system is used to track individuals on a campus, such as a university campus, a public location, a museum, a library, a factory, a park, etc. Individuals may be visitors, employees, security staff etc. The tag sensor or in vivo-type sensor may be placed on the students, for example, and information may be transmitted about the student's exact location at all times, even inside buildings where GPS is unavailable. Knowing the location of an individual may be beneficial for security purposes, e.g., doors may be locked and unlocked based on the location of tracked individuals. Further, information may be provided to the tracked individuals in a location-dependent manner, thereby improving campus visitor experience, increase security and streamline operations.

Use Case V: Agriculture

In one or more embodiments of the invention, the monitoring system described herein may be used in the agriculture industry. For example, sensor such as those described above may be used to obtain information about the fertility of soil and moisture content of soil. The system may be used specifically to conserve energy water resources and detection of water levels to enhance crop productivity. Selection methods for controlling irrigation based on different parameters may then be learned and applied. Specifically, tags may be placed on water tanks to track the amount of water inside. Tags may also be placed on non-stationary farming equipment to know the exact location of such equipment in a large agricultural field. In addition, drones may be used across the agricultural fields, where the drones are configured to house/carry the access points that communicate with the sensors on the crops and/or in the soil.

Use Case VI: Warehousing

In one embodiment of the invention, the monitoring system is used to track equipment, goods, shipments etc. The tracked equipment may include, but is not limited to forklifts, other types of vehicles, tools, etc. Further, a similar configuration may be used in other settings as well, for example in a baggage processing facility of an airport in order to track luggage as it is progressing through the facility. Such a system may result in a reduction in lost luggage. The monitoring system may further be used to detect bottlenecks, to strategically move equipment to locations where it is needed, etc., thus improving overall operations.

While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this disclosure, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as disclosed herein. Accordingly, the scope of the invention should be limited only by the attached claims. 

What is claimed is:
 1. A sensor system comprising: a battery that powers the sensor system; an IoT sensor that provides a sensing data for the sensor system, wherein the IoT sensor comprises an accelerometer that detects movement of the sensor system to obtain movement data of the IoT sensor; a transceiver that communicates with the IoT sensor in an IoT system; a processor that: receives the movement data from the IoT sensor, and controls an activation of the IoT sensor and a frequency of communication of the transceiver with the IoT sensor; and an IoT link that connects an access point to the IoT sensor, wherein the IoT sensor comprises one of the following states: a in-range state in which the IoT sensor is within a coverage range of an IoT network and is able to receive beans from the access point via the IoT link, and an out of range state in which the IoT sensor is not able to receive beacons from the access point via the IoT link, wherein when movement of the sensor system is not detected by the accelerometer, and the IoT is in the out of range state, the IoT enters a deep sleep mode to conserve battery power.
 2. The sensor system of claim 1, wherein when movement of the sensor system is detected by the accelerometer, the IoT sensor awakes from the deep sleep mode and searches for a beacon message transmitted by the access point and synchronizes to the beacon message to establish an association with the access point.
 3. The sensor system of claim 1, wherein when movement of the sensor system is detected by the accelerometer, and the IoT sensor is in range of the IoT network, the IoT sensor searches for a beacon message transmitted by an access point and synchronizes to the beacon message to establish an association with the access point.
 4. The sensor system of claim 1, wherein when movement of the sensor system is detected by the accelerometer, the IoT sensor sends a network status update to the IoT network to indicate movement and trigger one or more events.
 5. The sensor system of claim 3, wherein the sensor system transmits a data packet that includes the movement data to the access point and enters a deep sleep mode after the data packet is transmitted, and upon entering deep sleep mode, the IoT sensor only enters an active mode upon detection of movement by the accelerometer, when the IoT sensor is in range of the IoT network.
 6. The sensor system of claim 5, wherein the synchronization of the IoT sensor to the access point is updated each time the sensor system transitions between the deep sleep mode to the active mode.
 7. The sensor system of claim 6, wherein synchronization of the IoT sensor to the access point is omitted when no movement of the IoT sensor is detected by the accelerometer, to conserve battery power.
 8. The sensor system of claim 1, further comprising a charge controller that: controls a charging of the battery; monitors a battery status information; and communicates the battery status information to the processor.
 9. The sensor system of claim 7, wherein, in the event that the battery status information received by the processor indicates a low battery level, the processor: notifies the IoT sensor of the battery status information using the transceiver, reduces the frequency of communication of the transceiver with the IoT sensor, and deactivates the sensor.
 10. The sensor system of claim 9, further comprising one or more in-vivo sensors associated with the IoT sensor, and wherein the one or more in-vivo sensors are slave sensors to the IoT sensor in that a state of the one or more in-vivo sensors is based on a state of the IoT sensor, and wherein the one or more in-vivo sensors synchronize with the IoT sensor when the IoT sensor is in an active mode.
 11. The sensor system of claim 10, wherein the one or more in-vivo sensors are disposed in a dermal sensor attached to a surface of an asset.
 12. The sensor system of claim 10, wherein the one or more in-vivo sensors are disposed in a hermetically-sealed capsule made of a hydrophobic material.
 13. The sensor system of claim 10, wherein the IoT sensor signals the IoT sensor state to the one or more in-vivo sensors via an interface of the IoT sensor, and via a secondary sensor network distinct from the IoT network.
 14. A communication method comprising: measuring, by an accelerometer, movement of a sensor system comprising an IoT sensor in an IoT network, to obtain movement data, the sensor system comprising a battery that powers the sensor system and the accelerometer; determining a network status of the IoT sensor; transmitting, by the IoT sensor, the movement data to an access point in the IoT network; determining, based on the movement data and the network status, a state of the IoT sensor, wherein an active state indicates that the IoT sensor is in network range and is able to communicate with the access point, and wherein a deep sleep state indicates that the IoT sensor is one of: out of network range or in network range but not moving.
 15. The communication method of claim 14, further comprising, based on the movement data and network status: when movement of the sensor system is detected by the accelerometer, searching, by the IoT sensor, for a beacon message transmitted by the access point and synchronizing the IoT sensor to the beacon message to establish an association with the IoT network; and when movement of the sensor system is not detected by the accelerometer, entering into the deep sleep mode by the sensor system, to conserve battery power of the battery.
 16. The communication method of claim 14, wherein the sensor system further comprises: a transceiver that communicates with the IoT sensor in the IoT network; a processor that: receives the movement data from the accelerometer; and controls an activation of the sensor system and a frequency of communication of the transceiver with the IoT sensor based on the movement data.
 17. The communication method of claim 14, wherein the sensor system further comprises in-vivo sensors, the method further comprising: signaling, by the IoT sensor, the state of the IoT sensor to the in-vivo sensors via a secondary sensor network distinct from the IoT network, wherein the in-vivo sensors are slave sensors to the IoT sensor and take on a same state as the state of the IoT sensor.
 18. The communication method of claim 17, further comprising: synchronizing, by the in-vivo sensors, with the IoT sensor when the IoT sensor is in an active mode; and entering a deep sleep mode, by the in-vivo sensors, when the IoT sensor is in deep sleep mode.
 19. The communication method of claim 15, further comprising: transitioning from the deep sleep mode to an active mode of the sensor system, upon detection of movement of the sensor system by the accelerometer and based on the network status of the IoT sensor, wherein the synchronization of the IoT sensor to the IoT network is updated every time the sensor system transitions between the deep sleep mode to the active mode.
 20. A sensor system comprising: a battery that powers the sensor system; an IoT sensor that provides a sensing data for the sensor system, wherein the IoT sensor comprises an accelerometer that detects movement of the sensor system to obtain movement data of the IoT sensor; a transceiver that communicates with the IoT sensor in an IoT system; a processor that: receives the movement data from the IoT sensor, and controls an activation of the IoT sensor and a frequency of communication of the transceiver with the IoT sensor; and an IoT link that connects an access point to the IoT sensor, wherein the IoT sensor comprises one of the following states: a in-range state in which the IoT sensor is within a coverage range of an IoT network and is able to receive beans from the access point via the IoT link, and an out of range state in which the IoT sensor is not able to receive beacons from the access point via the IoT link, wherein when movement of the sensor system is detected by the accelerometer, and the IoT sensor is in range of the IoT network, the IoT sensor searches for a beacon message transmitted by an access point and synchronizes to the beacon message to establish an association with the access point. 